1
The Registration Sheet Is Starting to Break
DSAI2202 Lesson 1: Designing Relational Database Structures
00:00

Spreadsheets are wonderfully easy to start with when organizing school information. However, keeping all recordsβ€”such as students, courses, teachers, and sign-upsβ€”in one giant, overloaded sheet causes data to repeat endlessly and systems to break. When a student takes several classes, their personal details must be written down over and over again, creating messy duplication and serious maintenance challenges.

⚠️ Flat Registration Sheet Student: Sam (ID: 001) Course: Math, Science, Art Data repeats across rows! βœ“ Relational Database Table 1: Students (Sam) Table 2: Courses (Math...) Table 3: Enrolments (Link)

Core Concepts of Database Design

  • Data Duplication: When a course contains many students, course and teacher details repeat across many rows, wasting space and inviting errors.
  • Update Anomalies: If Sam changes his phone number and we only update it in one place, the sheet becomes full of conflicting information.
  • Requirement Analysis: Building a dependable design starts with spotting these problems and identifying entities, attributes, and relationships.

Why We Need Structure

A well-designed database prevents errorsβ€”such as letting the exact same student-course pair appear twice by mistake. By separating distinct concepts into properly structured tables, each row represents a single, consistent class of object, ensuring reliable operations.

Design Principle
Every design decision must be directly traceable to a stated requirement rather than assumed conventions, ensuring the architecture accurately models the real world.
The Registration Sheet Is Starting to Break